Skip to content

chore(deps): 15 dependencies evaluated. Key safe upgrades: eslint 8.3→8.57 (patch), j#17235

Open
isagoakira wants to merge 1 commit intofacebook:mainfrom
isagoakira:fix/deps-update-1778292235
Open

chore(deps): 15 dependencies evaluated. Key safe upgrades: eslint 8.3→8.57 (patch), j#17235
isagoakira wants to merge 1 commit intofacebook:mainfrom
isagoakira:fix/deps-update-1778292235

Conversation

@isagoakira
Copy link
Copy Markdown

🔧 依赖维护更新 — facebook/create-react-app

此 PR 由 Code Legacy Reviver 自动生成🤖

📋 更新摘要

15 dependencies evaluated. Key safe upgrades: eslint 8.3→8.57 (patch), jest 27.4→27.5 (minor), prettier 2.5→2.8 (patch), globby 11.0→11.1 (patch), lint-staged 12.1→12.5 (minor). High-risk packages flagged: puppeteer (10 major versions behind, bundled Chromium changes), husky (4.x→8.x config migration needed), lerna (4.x LTS but 8.x is current). web-vitals 2.x→3.x has API changes. @testing-library/react 12→13 is a reasonable step; 14+/15 require React 18 testing patterns.

📦 变更清单

🔴 eslint: ^8.3.0^8.57.0
8.3.0 (2019) is behind; 8.x line is still supported with bug/security fixes up to 8.57.0; safe minor upgrade within major version

🔴 prettier: ^2.5.0^2.8.8
2.5.0 is 3 minor versions behind within 2.x; 2.8.8 is latest 2.x with bug fixes; jumping to 3.x is risky due to config format changes

🔴 jest: ^27.4.3^27.5.0
27.4.3 (2021) is behind; 27.5.0 is latest in 27.x line with fixes; jumping to 29.x has breaking config changes (jest.config.js format)

🟡 puppeteer: ^12.0.1^21.6.1
12.0.1 (2020) is extremely outdated, 10+ major versions behind; puppeteer 13+ requires Chromium bundled separately; major upgrade with significant breaking changes

🔴 fs-extra: ^10.0.0^10.1.0
10.0.0 is 3 minors behind 10.1.0; jumping to 11.x has ESM-only release requiring module system changes

🟡 web-vitals: ^2.1.2^3.5.0
2.1.2 is 2 major versions behind; 3.x has API changes (onCLS/onFID renamed, attribution object restructured); test impact should be verified

🟡 @testing-library/react: ^12.1.2^13.4.0
12.1.2 (2022) is 1-2 major versions behind current 14.x/15.x; 13.x is a reasonable midpoint with some breaking changes; 14+/15 have React 18 concurrent mode changes

🔴 @testing-library/jest-dom: ^5.15.1^5.17.0
5.15.1 is behind within 5.x; jumping to 6.x has breaking changes (toBeInTheDocument removed, new matchers); safer to stay in 5.x line

🔴 execa: ^5.1.1^5.1.1
5.1.1 is latest in 5.x; 6.x+ moved to ESM and changed API significantly; staying on 5.x is safe for CommonJS projects

🔴 strip-ansi: ^6.0.1^6.0.1
6.0.1 is latest in 6.x; 7.x switched to ESM with breaking changes; safe to leave as-is

🟡 get-port: ^5.1.1^5.1.1
5.1.1 appears to be latest in 5.x; 6.x changed the default port algorithm; safe to leave as-is

🟡 lerna: ^4.0.0^4.0.0
4.0.0 is old but 4.x is still LTS; 5.x+ requires Node 14+ and changed package layout; 8.x is current but major jump; recommended: plan migration to 8.x separately

🔴 globby: ^11.0.4^11.1.0
11.0.4 is 3 minor versions behind within 11.x; 13.x+ switched to ESM; safe to update within 11.x

🔴 husky: ^4.3.8^4.3.8
4.x to 8.x/9.x has breaking config format changes (.husky directory structure, CLI changes); should be migrated in a dedicated PR

🔴 lint-staged: ^12.1.2^12.5.0
12.1.2 is 4 minor versions behind within 12.x with bug fixes; 13.x+ dropped Node 12 support; safe to update within 12.x

⚠️ 风险等级

🟡 Medium

📝 文件变更

  • package.json

Generated by Code Legacy Reviver

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 9, 2026

Hi @isagoakira!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla meta-cla Bot added the CLA Signed label May 9, 2026
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 9, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant